Disabling unit tests lead to a lack of visibility into why tests are ignored, a decline in code quality as underlying problems remain unaddressed,
and an increased maintenance burden due to the accumulation of disabled tests. It can also create a false sense of security about the stability of the
codebase and pose challenges for new developers who may lack the context to understand why tests were disabled. Proper documentation and clear reasons
for disabling tests are essential to ensure they are revisited and re-enabled once the issues are resolved.
This rule raises an issue when a test construct from Jasmine, Jest, Mocha, or Node.js Test Runner is disabled without providing an explanation. It
relies on the presence of a package.json file and looks at the dependencies to determine which testing framework is used.
